Routing of messages

ABSTRACT

A method to provide transfer of data without the use of a network from an application program to an embedded device. A routing service establishes a communication channel without the use of a local area network. The routing service then manages the control of this communication channel for the transfer of data and closes the channel in an appropriate period.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.11/021,568, filed Dec. 22, 2004, the entire contents of which isincorporated by reference herein in its entirety.

TECHNICAL FIELD

In general, the present subject pertains to communication systems andmore particularly to application software control of an embedded unit.

Background

Typically, third-party application software communicates through a localarea network to an embedded processor for managing an embedded devicecontrolled by the embedded processor. This application software willcommunicate through the local area network, utilizing standard protocolsuch as: HTTP (hyper text transport protocol), SOAP (standard protocolenabling remote procedure calls) messages, and TLS/SSL (transport layersecurity/secure socket layer).

Further, some of the services provided by application software mayexecute on the same computational platform for which manageability ofthe embedded device is sought. For example, a management console maygather inventory information from all computational platforms in anorganization. This inventory information may be gathered from theembedded manageability devices residing on an organization'scomputational platforms. As an additional example, the information maybe located in some type of non-volatile memory. The application softwaremay need to gather such information located within the control of theembedded device to provide, for example, information sharing betweenlocal and remote agents.

Simply returning information to the application software through a localdevice using normal network stacks will result in the information beingforwarded incorrectly. Either the TCP/IP (transmission controlprotocol/internet protocol) stack may not forward the information to anetwork adapter or the network will not return data packets back on thesame physical link from which they came.

DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a communication arrangement in accordancewith an embodiment in the present invention.

FIG. 2 is a block diagram depicting various protocol layers associatedwith an embodiment of the present invention.

FIG. 3 is a flow chart of a communication arrangement in accordance withan embodiment of the present invention.

FIG. 4 is a flow chart of a connect request in accordance with anembodiment of the present invention.

FIG. 5 is a flow chart of a read request in accordance with anembodiment of the present invention.

FIG. 6 is a flow chart of a close request in accordance with anembodiment of the present invention.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of a communication arrangement directlybetween operating system 20 of processor 15 and embedded device 30without using a local area network in accordance with an embodiment ofthe present invention. This communication arrangement can enable anapplication program 22 to provide out-of-band (OOB) management of thecommunication arrangement. OOB indicates that a system may be anoperating system agnostic. Typically, application programs communicatethrough a network utilizing standard protocols. As an example of such anarrangement, consider a management console of computational platform 10gathering inventory information from various computational platforms inan organization. This information may need to be gathered from embeddedmanageability devices (commonly referred to as embedded devices).However, simply sending the information to the embedded device through anormal network stack will result in information being incorrectlyforwarded.

Operating system 20 may be associated with the application program 22.Application program 22 is coupled to the operating system (OS) networkstack 24. Although application program 22 is shown within the OS 20,program 22 may be separate from the OS 20. Typical flow of messagesthrough operating system 20 is from OS network stack 24 to network LANcontroller 28 and via routing 29 to a local area network (not shown).

Incoming messages for embedded device 30 are received from the localarea network (not shown) through routing 42 to a network LAN controller44. Upon the initialization of operating system 20, routing service 25is bound to OS network stack 24 via a particular destination port.

When application program 22 uses the particular destination port number,which is an internet assigned number authority (IANA) transmissioncontrol protocol/internet protocol (TCP/IP) port number, routing service25 binds to this particular port number. Once this binding is completed,any messages sent to the OS network stack 24 with destination IP addressassigned to OS 20 and with the particular destination port number wouldbe routed by OS network stack 24 to routing service 25. When applicationprogram 22 communicates with an embedded device 30, it sends a messageusing standard network protocols to OS network stack 24. OS networkstack 24 may check the destination IP address and TCP destination portassociated with the message. OS network stack 24 then identifies themessage as either one which should be routed to an entity or one whichshould be routed to the routing service 25.

An embedded device in some embodiments may be a device that is placedwithin a computational platform. The embedded device may include a setof resources independent of the main resources of the computationalplatform, such as, a processor and a memory resources, for example.

Normally messages would be transmitted from OS network stack 24 throughnetwork LAN controller 28 and routed via network routing 29 to thenetwork.

In the present example, OS network stack 24 has determined from thedestination IP address and the TCP destination port that routing of themessage should be to routing service 25, for example.

Routing service 25 may then send a connect message through bus driver 26through bus 40 to the embedded device 30. Bus arrangement 40 may includea serial bus, a parallel bus, a PCI bus, a buffer, a switch, a memory ofvarious types, or a number of registers.

Bus 40 then passes the message through interface driver 32 of embeddeddevice 30 through network multiplex 34 to internal application program35 of embedded device 30. If the message is a connect message, forexample, the connect request may be successful.

Once this communication channel becomes established from routing serviceto internal application program 35, the message originally sent byapplication program 22 through OS network stack 24 to routing service 25is transmitted along the same communication channel as previouslymentioned to internal application program 35. This communication channelis from routing service 25, through bus driver 26, through bus 40,through interface driver 32, through network multiplexer 34 to internalapplication program 35.

When all the messages have been sent by routing service 25, or receivedby routing service 25, routing service 25 will then close one side ofthe communication channel that was previously established afterreceiving a close request from application program 35, for example. Thatis, routing service 25 will tear down the connection between bus driver26 and bus 40, and between bus 40 and interface driver 32.

In addition, embedded device 30 may receive input from the network viarouting 42 through local area network (LAN) controller 44. Such networkrouted messages are then sent to interface driver 33, through networkmultiplexer 34 to the internal application program 35. Further, embeddeddevice 30 may include an embedded processor 31 or other devices. Theembedded device may provide for execution of the internal applicationprogram 35. Embedded processor 31 may be implemented on a chip-set, inan embodiment. In other embodiment, embedded processor 31 as well asembedded device 30 may be implemented as part of a chip set, on a motherboard as a chip, or on a portion of a network interface card (NIC)inserted into a circuit card slot. However, the implementation is notlimited to these configurations. A chip is a semiconductor device.

Bus 40 transmits messages between routing service 25 and internalapplication program 35 and may be implemented on top of a peripheralcontroller interface such as PCl/PCI-X/PCI-Express, USB, etc. type busarrangement. Further, store and forward devices such as memories, etc.may provide the communication channel as well.

Operating system 20 may be implemented on a semiconductor devicefabricated by various technologies known to those of ordinary skill inthe art such as silicon, gallium arsenate, etc. This semiconductordevice or “chip” may include a processor 15 having an operating system20, an application program 22, OS network stack 24, routing service 25and bus driver 26.

FIG. 2 is a block diagram which maps various network protocol layerswhich may be used to communicate with software which handles each layer.The various protocols of 50 correspond to the protocol layers associatedwith operating system 20. The various protocols of 61 correspond to theprotocols associated with embedded device 30. The highest level protocolwithin writing system protocols is the application layer 51. On thehighest level of protocol stack 60 of the embedded device 30 iscapability module (CM) 61 which provides the highest level protocollayer. The application layer communicates and corresponds with thecapability module level 61 in the embedded device protocol stack 60.

The next lower layer within the protocol stack 50 of operating system 20is SOAP/HTTP encapsulation layer 52. This layer corresponds andcommunicates with SOAP/HTTP server 62 in the embedded device protocolstack 60.

The next lower layer in the operating system stack 50 is the transportlayer security (TLS) layer 53. The transport layer security 53communicates with and corresponds to transport layer security (TLS) 63within the embedded device protocol stack 60. The next lower layer ofthe protocol stack 50 of the operating system is a

BSD socket layer 54. The BSD socket layer 54 communicates with andcorresponds to local socket provider 64 through routing service protocol55. Routing service protocol 55 communicates with BSD socket layer 54.Routing service protocol 55 communicates with the local socket providerprotocol 64 of the embedded device protocol stack 60.

Lastly is shown the transmission control protocol/internet protocol(TCP/IP) or user datagram protocol/internet protocol 57. Device driverprotocol 58 communicates between device driver 65 of the protocol stack60 of embedded device 30 and routing service protocol 55.

As a result of the above-described processing by routing service 25, itcan be seen that a data transfer is shown excluding the use of a localarea network.

In FIG. 3, a flow chart of an embodiment of the method for routing isshown. This method is performed by routing service 25. Theimplementation for the processing described herein may take the form ofmachine-readable software code. This machine-readable software codemight be implemented in read-only memory, any non-volatile random accessmemory, flash memory, electronically programmable read-only memory, etc.

The method for routing of data is started and block 70 is entered.First, the routing service 25 initializes communication with device orbus driver 26, block 70. Next, routing service 25 binds to the portassociated with the TCP destination, block 72. The routing service 25 istypically bound to a particular designated TCP port when thecomputational platform 10 is initially started or is restarted. ThisIANA port couples OS network stack 24 to routing service 25.

Next, routing service 25 initializes an application socket pair, block74. That is, routing service 25 establishes the BSD socket layer from 54to 55 and a pseudo-socket from 55 to 64. Then routing service 25 awaitsthe socket requests coming from the socket layer 54 of operating system20 and the local socket provider 64 of embedded device 30.

When these socket requests are received by routing service 25, theappropriate connection between bus drivers 26 and 32 have been selectedand established.

The service 55 then waits for responses from the socket requests atblock 76. When a single socket request has been received, block 76transfers control to block 78. Block 78 determines whether the requestmay be a connect request to establish the communication channel fromrouting service 25 through bus driver 26 through bus arrangement 40,through bus driver 32 and network multiplexer 34 to internal applicationprogram 35. If the request is a connect request, block 78 transferscontrol to block 80 via the YES path. Block 80, which will be explainedin detail later, handles the connect request from routing service 25 andhost processor 15 and then transfers control, upon completion, to block76 to wait for subsequent socket requests.

If the request is not a connect request, block 78 transfers control toblock 82 via the NO path. Block 82 determines whether the request may bea read request for exchanging data between internal application program35 and routing service 25. If the request is a read request, block 82transfers control to block 84 via the YES path.

Block 84 handles the read request from either the application program 22of the operating system (HOST) or the internal application program 35 ofthe imbedded device (EP). When the read request is completed, block 84transfers control to block 76 to wait for socket requests.

If the request is determined to be neither a connect or read request,block 82 transfers control to block 86 via the NO path. This methoddetermines that the request should be a close request. That is, theclose request is the command to tear down the previously establishedcommunication channel from routing service 25 to internal applicationprogram 35 or communication channel from application program 22 torouting service 25, depending on the source of this request (HOST orEP). Since this is a close request, block 86 transfers control to block88. Block 88 handles the close request from either the routing serviceof the operating system or the internal application program of theimbedded device. Upon completion of the close, block 88 transferscontrol to block 76 to wait for socket requests. As a result of theabove-described processing, it can be seen that a data transfer is shownexcluding the use of a local area network.

In FIG. 4, a flow chart of an embodiment of the connect requestprocessing of block 80 is shown. Block 89 diagrammatically depicts theinput to the connect request 80 as being the socket identity. Block 90then determines the socket request is initiated from the application 22.Recall that the application program 22 is typically the one which canrequest the connection of the communication channel between theoperating system and the embedded device, although the embedded 30 mayalso request. If the socket request is not initiated from theapplication 22, block 90 transfers control via the NO path to block 93.Block 93 issues a socket request to the application. Then block 93transfers control to block 94.

If the connect request is from the application 22, block 90 transferscontrol to block 92 via the YES path. Next, block 92 issues a connectrequest to the embedded device, resulting in embedded processor socket.

Next, block 94 waits and determines whether the connect request has beensuccessfully completed. If the request does not complete within apredetermined time limit or is returned as being incomplete, block 94transfers control to block 96. Block 96 indicates a failure of theconnect request and ends the process.

When the connect request is successfully complete, block 94 transferscontrol to block 98 via the YES path. Then a socket pair (SP) isdetermined: HOST processor 15 and embedded processor 31. Then the socketpair for the application program 22 to internal application 35connection is stored in a data base by routing service 25. The processis ended.

In FIG. 5, an embodiment of the read request 84 from either theoperating system or embedded device is depicted in flow chart form. Theinput to the read request is the socket identity, block 101.

First, the socket pair structure is found from a data base indicatingthe host socket, block 102. Next, routing service 25 sets the socket ofthe embedded device (EP) with the socket pair of the data base, block104.

Next, block 106 sets a read/write buffer to read from the HOST socket.This assumes that the message is being transferred from the applicationprogram 22 to the internal application program 35. If the data transferhappened to be from internal application program 35 to applicationprogram 22, the buffer read would be from the embedded device 30.

Next, block 108 determines whether this request to read into the bufferwas successful. If the buffer request was successful, block 108transfers control to block 110 via the YES path. Block 110 then writesthe data. This corresponds to sending the data from the buffer throughbus driver 26, through bus arrangement 40, through bus driver 32 andnetwork multiplexer 34 to the internal application program 35 (EP) . Ifthe data transfer is from internal application program 35 to applicationprogram 22, the data flow and reading and writing would be performed bythe other socket of the socket pair (HOST). If the write is successful,the data is received by internal application program 35, block 112transfers control and ends the process.

If the attempted write was unsuccessful, block 112 transfers control toblock 114 via the NO path. Block 114 first closes the operating systemsocket, the initiator of the data request. Then block 114 closes theembedded device socket, the receiver of the data transfer request.

Then the socket pair is removed from the data base, block 116. Theprocess is then ended.

Similarly, for an unsuccessful read to the buffer, block 108 transferscontrol to block 114. Block 114 and block 116 perform as mentionedabove. Then the process is ended.

In FIG. 6, an embodiment of the close request 88 is depicted in flowchart form. Block 120 indicates the input being the socket identity.Next, the socket pair structure is found in the data base from thesocket identity, block 122. Next, block 124 determines whether thesocket identity is a type of embedded device socket (EP). If it is anembedded device, block 124 transfers control to block 128 via the YESpath. Block 128 closes the socket pair from the HOST socket. Then theprocess is ended.

If the socket type is not an embedded device socket, block 124 transferscontrol to block 126 via the NO path. In block 126, the embedded devicecloses the socket pair from the embedded device socket (EP). Then theprocess is ended.

The description and the drawings illustrate specific embodiments of theinvention sufficiently to enable those skilled in the art to practiceit. Examples merely typify possible variations. Portions and features ofsome embodiments may be included in or substituted for those of others.The scope of the embodiments of the invention encompasses the full ambitof the claims and all available equivalents. In some embodiments, thepresent invention relates to communicating by an application programwith an embedded device or processor. In other embodiments, the presentinvention may pertain to communication between an application program 22and an embedded device 30 without the use of any local area network28-29, 42-44.

As a result of the above-described processing by routing service 25, itcan be seen that a data transfer is shown excluding the use of a localarea network. Further, routing service 25 may be implemented on asemiconductor device. This avoids further costs of “add-on” hardware.

Although some embodiments of the invention have been illustrated, andthose forms described in detail, it will be readily apparent to thoseskilled in the art that various modifications may be made thereinwithout departing from the spirit of these embodiments or from the scopeof the appended claims.

1-3. (canceled)
 4. A computational platform comprising: an embeddeddevice operable to receive a message from an application program; anoperating system including an operating system network stack, theoperating system operable to provide the message for routing to theembedded device; a routing service bound to the operating network stackthough a particular destination port; a network LAN controllercommunicatively coupled to the operating system network stack; whereinthe operating system network stack is operable to receive the messagefrom the operating system and to route the message to the embeddeddevice based on a destination IP address and an indication of theparticular destination port being induced in the message, and otherwiserouting the message to the network LAN controller.
 5. The computationalplatform of claim 4, wherein the embedded device includes a processorand a memory resource that are independent of a set of main resources ofthe computational platform.
 6. The computational platform of claim 4,further including: a bus driver coupled to the routing service; a buscoupled to the bus driver, and the bus driver coupled to the embeddeddevice, wherein the routing service is operable to send messages to theembedded device though the bus driver and the bus.
 7. The computationalplatform of claim 6, wherein the bus is serial bus.
 8. The computationalplatform of claim 6, wherein the bus is a PCI bus.
 9. The computationalplatform of claim 4, wherein the routing service is operable to receiveone or more messages sent from the embedded device, and to route the oneor more messages to the application program through the operating systemnetwork stack.
 10. The computational platform of claim 4, furtherincluding; a second network LAN controller coupled to the network LANcontroller and to the embedded device, wherein the network LANcontroller is operable to route one or more messages to the network LANcontroller to the embedded device through the second network LANcontroller.
 11. The computational platform of claim 4, wherein thenetwork LAN controller is operable to receive one or more messages fromthe embedded device, and to route the one or more messages to theapplication program through the operating network stack.
 12. A methodcomprising: binding a routing service to an operating system networkstack through a particular destination port; communicatively couplingthe operating system network stack to a network LAN controller;receiving at the operating system network stack a message; determiningif the message is to be routed to an embedded device by determining ifthe message includes both a destination IP address and a designation ofthe particular destination port that are associated with the embeddeddevice; routing the message to the routing service through theparticular destination port if a determination is made that the messageis to be routed to the embedded device, and routing the message to thenetwork LAN controller if the message is not to be routed to theembedded device.
 13. The method of claim 12, wherein binding the routingservice includes: establishing a socket layer between a BSD socket layerin the operating system network stack.
 14. The method of claim 13,further including: establishing a pseudo-socket between the routingservice and a local socket provide of the embedded device.
 15. Themethod of claim 14, further including: receiving a socket request fromthe BSD socket layer; determining that the socket request is a connectrequest to establish a communication channel from the routing service tothe embedded device; and issuing a connect request to the embeddeddevice.
 16. The method of claim 14, further including: receiving asocket request; determining that the socket request is a read request;setting a read/write buffer to read from a HOST socket; determining ifthe request to read the read/write buffer was successful, and if therequest to read was successful, then writing data obtained from theread/write buffer.
 17. The method of claim 14, further including:receiving a socket request; determining that the socket request is aclose request; and tearing down a previously established communicationchannel between the routing service and the embedded device.
 18. Anon-transitory machine-readable medium that provides machine-readableinstructions, which when executed by one or more processors, cause theone or more processors to perform operations comprising: binding arouting service to an operating system network stack through aparticular destination port; communicatively coupling the operatingsystem network stack to a network LAN controller; receiving at theoperating system network stack a message; determining if the message isto be routed to an embedded device by determining if the messageincludes both a destination IP address assigned to the operating systemnetwork and a designation of the particular destination port; routingthe message to the routing service through the particular destinationport if a determination is made that the message is to be routed to theembedded device, and routing the message to the network LAN controllerif the message is not to be routed to the embedded device.